|
A process-driven application is a software application that is driven by an underlying process or workflow engine where the process can be exposed and reused. In effect all applications are process-driven and the logic of any application can be extrapolated into a flowchart to represent the logical process of execution. Process-driven applications are a growing trend in enterprise solutions involving humans, systems or both. Recently, Microsoft introduced the Windows Workflow Foundation (“WF”) which provides developers with the ability to separate application flow from application execution. A Microsoft product to use this approach is BizTalk Server, where orchestrations represent the order of execution. Both technologies provide graphical tools to manipulate processes and can form part of a process-driven application. They provide the process engine required to drive the application. The term process-driven application was popularized by ( K2 ) in 2008 when describing applications driven by processes, and originally referred to applications driven by their business process management ("BPM") software known as (K2 blackpearl ). The term has now gained wider acceptance and refers to any application driven by a process engine. == History == The first software applications were considered procedural in that they were composed of multiple procedures that were called in a predefined order. This predefined order could be static, such as in applications not requiring input, or dynamic based on input either from humans or other sources. In effect, the entire execution path could be directly mapped onto a flowchart which would take into account all path changes based on input. In those days, it was the norm for all applications to start out as a flowchart and then move forward from there although this has now changed as organizations move towards Rapid Application Development ("RAD") methodologies. Even today's applications using today's techniques of object-oriented programming can have their execution logic represented using a flowchart. Now consider that the humble flowchart forms the basis of all processes in use today. Whether it's accounting, business, engineering, etc., the humble flowchart was the first, so to speak. All process models attribute their roots to the flowchart. Taking the above into account, it was only a matter of time before technologists realized this gap and started to look for tooling to support the ongoing design and maintenance of these processes. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Process-driven application」の詳細全文を読む スポンサード リンク
|